In my opinion, this event doesn't make sense. If we want to detect event cancellations, we should do it once for all events rather than creating separate packets and events for everything. Using the same logic, one could cancel vehicle damage, ped damage, object damage, weapon shots, etc.

A potentially better (though still not ideal) solution could be an event like onEventCancelled, triggered when any event is canceled on the client side. However, I believe this should be an option in mtaserver.conf because some server owners might prioritize performance and not want the server to constantly process packets about canceled events, such as decorative peds damage, weapon fire, etc.

In my opinion, this event doesn't make sense. If we want to detect event cancellations, we should do it once for all events rather than creating separate packets and events for everything. Using the same logic, one could cancel vehicle damage, ped damage, object damage, weapon shots, etc.

A potentially better (though still not ideal) solution could be an event like onEventCancelled, triggered when any event is canceled on the client side. However, I believe this should be an option in mtaserver.conf because some server owners might prioritize performance and not want the server to constantly process packets about canceled events, such as decorative peds, weapon fire, etc.

That's too complicated, because there's no need to detect cancellation of every event on the server-side, onClientPlayerDamage is a highly exploitable event on the client-side, which can't really be detected otherwise, except with custom events, which are quite easy for a cheater to prevent from sending, even from Lua.

So if gamemode cancels this event by default (what most advanced servers do) this will add unnecessary network / CPU overhead? Is this correct?

Wouldn't it be better to make it toggleable via server config for example?
Players can receive a lot of damage and this will flood server with useless packets if gamemode cancels this event by default.

That's too complicated, because there's no need to detect cancellation of every event on the server-side, onClientPlayerDamage is a highly exploitable event on the client-side, which can't really be detected otherwise, except with custom events, which are quite easy for a cheater to prevent from sending, even from Lua.

If cheaters can cancel the onClientPlayerDamage event, they can just as easily cancel other events like onClientVehicleDamage, onClientObjectDamage, or onClientPedDamage. I understand your point that they mostly focus on themselves and possibly their vehicle, but as I mentioned earlier, I think adding a toggle option in mtaserver.conf would be a good approach. Many servers naturally cancel this event depending on the game mode.

Then I'll add an option to mtaserver.conf @starfleet001 & @FileEX

This pull request is being closed in favor of a better implementation. Read more: https://discord.com/channels/801330706252038164/1300970029562597457/1342576783064694786